Skip to content

feat(build): configure standalone output for EC2 deployment#39

Open
itinsecurity wants to merge 1 commit intomainfrom
chore/standalone-ec2-output
Open

feat(build): configure standalone output for EC2 deployment#39
itinsecurity wants to merge 1 commit intomainfrom
chore/standalone-ec2-output

Conversation

@itinsecurity
Copy link
Copy Markdown
Owner

Summary

  • Adds binaryTargets = ["native", "linux-arm64-openssl-3.0.x"] to prisma/schema.prisma so the Prisma client includes the ARM64 binary for EC2 (linux/arm64)
  • Adds prisma.deploy.config.cjs and prisma.deploy.config.mjs — minimal Prisma configs for running prisma migrate deploy on EC2 without loading @prisma/config or its transitive effect dependency (not bundled in the standalone artifact)

Test plan

  • Build succeeds locally (next build with output: "standalone")
  • Prisma client generates with linux-arm64-openssl-3.0.x binary target present
  • prisma migrate deploy --config prisma.deploy.config.mjs runs without import errors on the EC2 instance

🤖 Generated with Claude Code

Add Next.js standalone output mode and Prisma ARM64 binary target
to support deployment to EC2 (linux/arm64).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant